Telemachus.

A team uploads its documents, talks to a model about them, runs workflows over them, shares the results with exactly the people who should see them, and does all of it on a machine the team controls.

Start here

• Telemachus for Developers

  The book: how the platform is built, and the decisions that were expensive to learn. Also as a PDF.

• Integrator's guide

  Putting your own product on the platform: theme the console, ship tools, serve your own screens and API.

• Read me first

  What it is, what runs today, and how to get it running.

• Reference

  Generated from the source: every route, tool, workflow, permission and plugin seam.

Reference

Generated by telemachus-docs from the route table, the tool registry, the plugin loader, the workflow specs and the permission catalog — and gated in CI, so it cannot drift from the code.

• HTTP API — every route with its authentication, permission and feature flag
• Tools — schema, permission and source for each
• Workflows — the shipped specs, step by step
• Permissions — the catalog and the role matrix
• Plugins — loaded plugins and the seams a plugin may fill
• SDK — the authoring surfaces
• 日本語版

Operating

• Document Repository & S3 Endpoint — setup & test runbook
• Multi-Tenancy — operator runbook
• Secrets at rest — operator runbook
• Workflow Engine — setup & test runbook

Design

Why each subsystem is shaped as it is, with the data shapes and the decisions.

• Telemachus — Platform Design
• AI Workload Scheduler (Queue, Governor & Executors)
• Beta Onboarding Experience (Skinnable & Admin-Configurable)
• Kickoff Decisions
• Document Repository — binary documents behind an S3 API
• Document sharing, with permissions
• Document workflows: uploads that trigger processing
• Documentation generation
• Knowledge Graph
• Localization (i18n) & the Localization Manager
• Multi-Tenancy — one instance, many companies
• Nix Packaging (Reproducible Build, Run & Deploy)
• Pull-model executors: inference hosts that come to the work
• Quotas
• RBAC & Teams
• Onboarding & Tenant Provisioning (Hosted / SaaS)
• Workflow Engine — plugins that process in steps

The code

The reference implementation is Racket 9.2 under refimpl/racketmaximus/; Nix is the toolchain. The durable product is the contract — the SDK, the APIs, the security model, the protocols — so a second implementation can target the same specs.

github.com/IoTone/Telemachus · Contributing